Skip to content

Conversation

@rvedotrc
Copy link
Contributor

No description provided.

@rvedotrc rvedotrc changed the title Import legacy Git content as a starting point "Import" existing Git modules as a starting point Apr 15, 2025
Copy link
Contributor

@adamblanchard adamblanchard left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's reasonable to get all the legacy content in this repo, to make it easier to move around and iterate on 👌

I'm not sure I follow the value of these "simple" modules that link to the old modules.

If we want to go ahead and move over modules in advance, then i suggest we follow the format:

  • Create a "Legacy" course directory
  • Copy over full module content into their own sub directory e.g. "Git"
  • Probably once we have finalised the new courses, we can remove Legacy. But it also serves no harm to keep it in place during the transition, if we find ourselves referring to it. It's easier to read than all the independent repos.

@rvedotrc
Copy link
Contributor Author

Superseded by #16

@rvedotrc rvedotrc closed this Apr 21, 2025
@rvedotrc rvedotrc deleted the legacy-git branch April 30, 2025 04:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants